The Organizational Information Requirements (OIR) explain why the organization needs information. They translate business, operational, and asset management goals into clear information needs that inform project-level requirements.
These OIRs provide the strategic context for the EIR and ensure that information delivered during the project supports real operational outcomes after handover.
| Type | Information needs | Purpose of information |
|---|---|---|
| People | Roles responsible for asset operation, maintenance, and compliance | Ensure accountability and clear ownership of information |
| Process | Maintenance planning, risk management, reporting, and lifecycle cost processes | Support operational workflows and regulatory reporting |
| Technology | Structured asset data suitable for CAFM and asset management systems | Enable system integration, analysis, and long-term usability |
Process: Register of maintainable assets with associated maintenance plans.
Purpose: Enable preventative maintenance and reduce reactive maintenance activities.
Process: Capture a list of new assets (as defined in the AIR) with unique identifiers.
Purpose: Ensure all assets are registered within the CAFM system at handover.
Process: Capture and report risks including description, impact, probability, priority, mitigation, and responsible party.
Purpose: Support internal governance and corporate health and safety reporting.
Process: Record utility costs per square foot and asset cost data (acquire, own, dispose).
Purpose: Enable KPI tracking, benchmarking, and board-level decision-making.
The OIR remains high-level and strategic. It does not define how information is delivered. The EIR and Scope translate these organizational needs into project-specific information requirements, responsibilities, and deliverables.